Feature/Trident operator#70
Conversation
| compliance-source-namespace: openshift-marketplace | ||
| compliance-channel: stable | ||
| ### Trident | ||
| trident: 'false' |
…m on the hub by default
…for local secrets and vault secrets, adding connection values in helm chart
…and not from the cluster its running policies against
| @@ -0,0 +1,14 @@ | |||
| apiVersion: trident.netapp.io/v1 | |||
| kind: TridentBackendConfig | |||
…ggle due to policy only running if files exist
…on from configmaps, adding support for cert authentication
bcarr-rh
left a comment
bcarr-rh
left a comment
There was a problem hiding this comment.
Need to add the new labels to the _example in clustersets for the ci tests to pass. If you need to lookup something like a secret you will need to create the yaml that you are looking up in the tools/testdata folder with dummy values. There should be some examples in there
| @@ -1,3 +1,327 @@ | |||
| <<<<<<< HEAD | |||
There was a problem hiding this comment.
looks like the merge didnt go well
| apiVersion: policy.open-cluster-management.io/v1 | ||
| kind: Policy | ||
| metadata: | ||
| name: policy-trident-operator-install |
There was a problem hiding this comment.
I guess it doesnt really matter but can this name match the file name?
| kind: ConfigurationPolicy | ||
| metadata: | ||
| name: trident-orchestrator | ||
| namespace: policies-autoshift |
There was a problem hiding this comment.
I think the namespace should either be removed or replaced with {{ .Values.policy_namespace }}
| kind: ConfigurationPolicy | ||
| metadata: | ||
| name: trident-orchestrator-test | ||
| namespace: policies-autoshift |
There was a problem hiding this comment.
namespace should either be removed or replaced with {{ .Values.policy_namespace }}
2 participants
The policies automate the deployment of the Trident Operator and its Orchestrator operand, while also integrating full lifecycle management for Trident resources including backendconfigs, storage classes, and related configurations.